Aggregation system for item retrieval

ABSTRACT

Various systems, mediums, and methods herein describe mechanisms that enable a user to send a request from her smartphone to multiple retriever devices, such that an item may be retrieved for the user. At least one of the users of the retriever devices may accept the request to retrieve the item for the requesting user. The retrieving device may send an acceptance message to the requester&#39;s smartphone to confirm that the item may be retrieved for the requesting user. In such instances, a retrieval fee may be transferred to the retrieving user&#39;s account accessible with the retriever device that accepted the request.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/244,533, filed Aug. 23, 2016, which is hereby incorporated byreference in its entirety.

BACKGROUND

In various circumstances, people are commonly found waiting in lines.For example, people may wait in a line to get tickets at a kiosk, aticket counter, and/or a check-out station, among various otherlocations, possibly in public areas. In some instances, people may waitin such lines to get tickets for public transportation, such as traintickets, bus tickets, ferry passes, and/or airline boarding passes,among other possible items. Further, people may also wait in lines toget items at a store, possibly where people may wait in a line tocheckout items at a given checkout counter. Yet further, people may alsowait in a line to get food at a fast casual restaurant, possibly wherethe each patron may wait in the line to make an order for food at therestaurant's ordering counter. As contemplated above, there are variousscenarios where users may have to wait in lines, particularly makingsuch experiences undesirable for the users. Further, considering thenumber of times that the users may wait in lines throughout a given day,the user experiences may be increasingly more inconvenient, inefficient,and probably undesirable.

As demonstrated in the various scenarios considered above, there is muchneed for improving various processes related to people waiting in lines,which can be achieved through technological advancements in variousaspects of computer technology in the realm of computer networks. Forexample, various improvements may be achieved with systems, mobiledevices, and/or network topologies associated with people waiting inlines, various wait times, and/or other delays, as described in thescenarios above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an exemplary system, according to an embodiment;

FIG. 1B illustrates an exemplary system with mobile devices, accordingto an embodiment;

FIG. 1C illustrates an exemplary system with the one or more tokens,according to an embodiment;

FIG. 1D illustrates an exemplary system with confirmations displayed bymobile devices, according to an embodiment;

FIG. 2A illustrates an exemplary system with mobile devices, accordingto an embodiment;

FIG. 2B illustrates an exemplary system with the one or more tokens,according to an embodiment;

FIG. 2C illustrates an exemplary system with the one or moreconfirmations, according to an embodiment;

FIG. 3 illustrates an exemplary system with a mobile device, accordingto an embodiment;

FIG. 4 illustrates an exemplary system with another mobile device,according to an embodiment;

FIG. 5 illustrates an exemplary system with multiple mobile devices,according to an embodiment;

FIG. 6 illustrates an exemplary system with multiple mobile devices,according to an embodiment;

FIG. 7 illustrates an exemplary method, according to an embodiment; and

FIG. 8 illustrates an exemplary system, according to an embodiment.

Embodiments of the present disclosure and their advantages may beunderstood by referring to the detailed description herein. It should beappreciated that reference numerals may be used to illustrate variouselements and features provided in the figures. The figures mayillustrate various examples for purposes of illustration and explanationrelated to the embodiments of the present disclosure and not forpurposes of any limitation.

DETAILED DESCRIPTION

As described in the scenarios above, there may be various circumstanceswhere a user may have to wait for an item, such as the user waiting in aline to get a train ticket from a ticket kiosk, as contemplated above.However, consider a scenario where the user is waiting towards the backof a longer line to get the train ticket from the kiosk. Further,consider that the user is in a hurry to get a ticket to get on the nexttrain, possibly approaching the train station. As such, the user may bewaiting in the line, observing each individual person ahead in the linego through the same process of obtaining a ticket. For example, theprocess may involve selecting menu options displayed by the kiosk,inserting funds or a credit card into the kiosk, and retrieving a ticketfrom the kiosk. Thus, the user may be painfully watching each individualgo through the same process, possibly knowing that the user is likely tomiss the approaching train due to the delay in waiting for eachindividual complete the process. In such circumstances, the user mayfind the experience undesirable based on the inconvenience and/orinefficiency involved with each individual ahead having to complete thesame process to receive a single ticket.

In view of such scenarios above, the systems described herein mayresolve the problems associated with the user waiting in various linescontemplated above. For example, consider the scenario of the userwaiting towards the back of the longer line, possibly referred to as therequesting user. In practice, the requesting user may be able to open amobile application on a smartphone, where the application may beconfigured to request, e.g., ping, message, and/or communicate with,other mobile devices of users ahead in the line. In particular, therequesting user may request the other users to purchase a ticket for therequesting user. In various circumstances, the users ahead in the linemay be selected by the requesting user, and in some instances, the usersahead in the line may be identified by the system. In some instances,the system may intelligently locate the other users ahead in the linebased on the geo-location of the requesting user's smartphone andpossibly also the geo-locations of the other users' mobile devices aheadin the line, where the system may display the other users on therequesting user's smartphone. Further, the system may intelligentlylocate other users ahead in the line that may be willing to retrieve aticket for the requesting user, potentially based on the other users'accounts, profiles, and/or transaction histories, possibly indicatingprevious acceptances of such requests and/or similar requests.

In some embodiments, specific users ahead in the line may be selectedbased on the urgency of the requesting user to make a purchase. In someinstances, the users may be selected in situations where there may bemultiple users between the requesting user and the kiosk described inthe scenarios above. Further, the requesting user may select a userahead in the line based on various factors, including the limited numberof items a single user may purchase per transaction, the number of itemsexpected and/or estimated to be purchased by the user ahead in the line,and/or the number of items requested by the requesting user, among otherpossible factors. For example, consider another scenario where the kioskallows each user to purchase a maximum of six items per transaction.Further, consider that a user ahead in the line may be expected topurchase four items and the requesting user may need four items as well.In such instances, the user ahead in the line expected to purchase fouritems may not be selected. Yet, in some instances, this user ahead inthe line may be selected to purchase an additional two items for therequesting user, in conjunction with one or more other users ahead inthe line that may be willing to purchase the remaining two items for therequesting user. Yet further, in some instances, the requesting user maywish a single user ahead in the line to purchase all the items requestedby the requesting user, possibly where the requested tickets may bepurchased with reserved seating, such that if multiple users ahead inthe line fulfill the request, the seats may be separated in differentareas. As such, in some instances, the system may identify a single userahead in the line willing to accept the request to retrieve multipletickets for the requesting user.

In some embodiments, the system may send the requesting user an image ofthe user ahead in the line that retrieves the ticket for the requestinguser. Further, the system may send the retrieving user an image of therequesting user. As such, the retrieving user and the requesting usermay identify each other, such that the retrieving user may physicallypass along and/or transfer the ticket to the requesting user, possiblyin exchange for a retrieval fee. In some instances, the system maydetermine the amount of the retrieval fee that the requesting user maybe required to pay the retrieving user based on the retrieving userobtaining the ticket for the requesting user. As such, the requestinguser's image may also be used to transfer the retrieving fee from therequesting user to the retrieving user. Yet further, the system mayelectronically transfer the retrieving fee from the requesting user'saccount to the retrieving user's account, among various otherpossibilities to transfer the retrieving fee, including third-partytransfers. As such, the various exchanges described herein may be madephysically and/or electronically based on a number of circumstances.

Notably, the retrieving user may obtain tickets for herself and therequesting user to seamlessly make a single transaction at the kioskdevice, possibly based on a mobile application on the retrieving user'ssmartphone. In some instances, based on accepting the request fortickets from the requesting user, the retrieving user may be able tomove her smartphone approximately four centimeters from the kiosk deviceto make a single transaction to obtain tickets for her and therequesting user, possibly utilising near field communication (NFC) tomake the transaction. As such, the system may be configured to aggregatemultiple transactions into a single transaction, possibly numeroustransactions into a single transaction.

Yet further, consider another scenario where multiple requesting usersin the back of the line request tickets from the retrieving userdescribed above. In such instances, the multiple requests may also bedetected by the system, such that the system may aggregate, combine,and/or consolidate the requests into a single combined request that issent to the retriever user's smartphone. In such instances, theretrieving user may make a single acceptance to retrieve a number ofrequested tickets from the multiple requesting users. In practice, theretrieving user may make the single acceptance, e.g., one touch input tothe mobile application on her smartphone, and move her smartphone nearthe kiosk device to obtain the multiple tickets requested from themultiple requesting users using NFC, as described above. Alternatively,the retrieving user may select only one or more requests from themultiple requests, where the selected requests may be aggregated to makea single transaction as described above. As such, in practice, theretrieving user may obtain tickets for multiple requesting users waitingin a longer line, possibly obtaining retrieval fees from each requestinguser in exchange for the tickets retrieved for each requester user.Thus, the retrieving user's account may accumulate numerous retrievalfees from the multiple requesting users. As such, the system may beconfigured to aggregate numerous transactions into a single transactionto improve efficiencies associated with the various waiting processesdescribed, thereby making such processes more convenient for the users.

In some embodiments, the system may detect a requester user waiting in aline, possibly based on the GPS coordinates of the user's smartphoneindicating incremental movements as the requesting user moves in theline. Further, the system may determine that the requesting user maywant to make a purchase by requesting the other users ahead in the lineto retrieve a ticket for the requesting user. In such instances, thesystem may determine which others users ahead in the line may be willingto retrieve the ticket for the requesting user, as well users that maybe willing to satisfy any requirements specified by the requesting user,possibly involving a requirement as to a time by which the requestedticket must be retrieved, a quantity of the tickets requested, and/orthe types of tickets requested, among other possibilities. Thus, basedon the user's request for the ticket, the system may provide therequesting user with a list of the other users ahead in the line willingto retrieve the ticket and satisfy the one or more requirements, wherethe list may be displayed on the requesting user's smartphone, such thatthe smartphone may be enabled to send the request to one or more of theother users to retrieve and/or purchase the ticket for the requestinguser.

FIG. 1A illustrates an exemplary system 100, according to an embodiment.As shown, a user 102 may be the requesting user described above,possibly where the user 102 may be in a hurry to get an item, such as aticket item, from the kiosk device and/or system 108, possibly to get onthe next train. In particular, there may be one or more users ahead inthe line to the kiosk device 108. For example, as shown, the user 104and the user 106 may be ahead of the user 102 in the line to the kiosk108. Notably, the users 102, 104, and/or 106 are shown for purposes ofexamples and illustration. Thus, there may be multiple other usersbetween the user 102 and the kiosk 108, as provided in the scenariosdescribed above involving the longer waiting lines. It should also benoted that the kiosk device 108 may, in some instances, take the form ofa boarding pass kiosk, a train ticket kiosk, a ticket counter, acheck-out station, a check-out counter, a point-of-sale (POS) device,among other possible devices, such as an automated teller machine (ATM).

Further, it should be noted that the users 102, 104, and/or 106 may bein a line, such as single file line, such that the user 104 is in frontof the user 102 and further the user 106 is in front of the user 104. Invarious circumstances, the line may move, possibly based on the users102, 104, and/or 106 moving towards the kiosk device 108. Further, theline may change based on various factors, such as the movements of theusers 102, 104, and/or 106, and/or possibly where the line may bendaround objects. Yet further, the line may get longer based on otherusers joining the line or the line may get shorter based on the users104 and/or 106 leaving the line.

FIG. 1B illustrates the exemplary system 100 with mobile devices 122and/or 126, according to an embodiment. As shown, the system 100 mayinclude the users 102, 104, and/or 106 described above, along with thekiosk device 108. Further, the user 102 may have the mobile device 122and the user 106 may have the mobile device 126, possibly where themobile devices 122 and/or 126 take the form of smartphones. Yet, themobile devices 122 and/or 126 may also take the form of wearablecomputers, laptop computers, and/or tablet computers, among other typesof computing devices configured to communicate electronically.

In some embodiments, the system 100 may detect a distance 110 betweenthe mobile device 122 and the kiosk 108, possibly based on detecting theglobal positions system (GPS) coordinates of the mobile device 122, andpossibly also based on the GPS coordinates of the kiosk device 108. Assuch, the system 100 may generate a request 112 for the user 102,possibly based on detecting the user 106 is ahead in the line, where theuser 102 is a distance 110 from the kiosk 108. Further, the request 112may be generated based on the system 100 determining and/or identifyingthe user 106 is willing to retrieve an extra ticket for the user 102.For example, the system 100 may determine the user 106 is willing toretrieve the ticket item 109 based on account information, profileinformation, and/or transaction histories associated with the user 106,possibly indicating previous acceptances of requests similar to therequest 112. As such, the generated request 112 may be displayed by themobile device 122, possibly so the user 102 may view, modify, and/orchange the request 112. It should be noted that the request 112 may alsobe created by the user 102 with the mobile device 122, as describedherein.

In some embodiments, the generated request 112 may be transmitted to theuser 106. For example, the generated request 112 may be transmitted fromthe mobile device 122, also referred to as the requester device 122. Inparticular, the generated request 112 may be transmitted from therequester device 122 based on an input received by the requester device122, such as a touch input received from the requesting user 102 on abutton that indicates, “Send the Request 122,” for example. As such, thetransmitted request 112 may be sent to the mobile device 126, alsoreferred to as the retriever device 126. In particular, the transmittedrequest 112 may be sent to the retriever device 126 based on thewireless signals 132, possibly including short-wavelength radio waves inthe radio band of 2.4 to 2.485 GHz, such as Bluetooth®, for example.Yet, some instances, the transmitted request 112 may be sent to thesystem 100, possibly including one or more cloud networks and/or basestation networks, and further transferred from the networks to theretriever device 126.

In some embodiments, the retriever device 126 may receive the request112 transmitted from the requester device 122, possibly based on thewireless signals 132 described above. Yet, in some instances, theretriever device 126 may receive the request 112 transmitted from theone or more cloud networks of the system 100 described above. As such,the retriever device 126 may display the transmitted request 112. Thus,in response to the transmitted request 112, the retriever device 126 maytransmit an acceptance message 116 that indicates the user 106 iswilling to retrieve an extra item 109 from the kiosk device 108 for theuser 102. In particular, the acceptance message 116 may be transmittedin response to an input received by the retriever device 126, possibly atouch input from the user 106 on a button that indicates, “Accept theRequest 122,” for example. In some instances, the acceptance message 116may be transmitted to the requester device 122 to accept the request112, possibly where the acceptance message 116 is transmitted based onthe communication signals 136 that may follow the same or similarcommunication protocols as the wireless signals 132 described above.Yet, in some instances, the acceptance message 116 may be transmitted tothe one or more cloud networks and/or base station networks describedabove such that the message 116 may be transferred and/or forwarded tothe requester device 122 from the networks. It should be noted, in someinstances, the generated request 112 may include a proposal to pay aretrieval fee in exchange for the user 106 retrieving the ticket item109 for the user 102. As such, in some instances, the acceptance message116 may indicate the user 106 is willing to retrieve the ticket item 109from the kiosk device 108 in exchange for the retrieval fee.

FIG. 1C illustrates the exemplary system 100 with the one or more tokens140, according to an embodiment. As shown, the system 100 may includethe users 102, 104, and/or 106 described above, along with the kioskdevice 108. Further, the user 102 may have the requester device 122 andthe user 106 may have the retriever device 126, as described above.

In some embodiments, the system 100 and/or the requester device 122 maydetermine the request 112 for the one or more items 109 that isavailable from the kiosk device 108. For example, the system 100 and/orthe requester device 122 may generate the request 112 based on the oneor more distances 110 from the requester device 112 to the kiosk device108. Further, the request 112 may be transmitted to the retriever device126 to request the user 106 to retrieve the one or more items 109 fromthe kiosk device 108. In some instances, the request 112 may betransmitted to the retriever device 126 based on the wireless signals132 described above. As noted, the request 112 may be transmitted to theretriever device 126 within the distance 110 from the requester device122 to the kiosk device 108.

As noted above, in response to transmitting the request 112 to theretriever device 126, the system 100 and/or the requester device 122 mayreceive the acceptance message 116 from the retriever device 126 thatindicates an acceptance by the user 106 to retrieve the one or moreitems 109 from the kiosk device 108 for the user 102. Yet, in responseto the receiving the acceptance message 116, the system 100 and/or therequester device 122 may generate the token 140 for the retriever device126 based on the determined request 112 for the one or more items 109.For example, the token 140 may be generated based on the number oftickets requested, the type of tickets requested, and/or the cost of thetickets requested, among other requested instructions in the request112. As such, the generated token 140 may be transmitted to theretriever device 126 for the user 106 to retrieve the one or more items109 from the kiosk device 108. In particular, the generated token 140may be transmitted to the retriever device 126 based on the wirelesssignals 132, possibly including the 2.4 to 2.485 GHz radio waves.

In some embodiments, the retriever device 126 may transfer the token 140with the request 142 to the kiosk device 108 for the ticket items 109for the requesting user 102 and the retrieving user 106. Yet, in someinstances, the retriever device 126 may be positioned approximately fourcentimeters from the kiosk device 108 to transfer the token 140 to thekiosk device 108 with the wireless signals 136, possibly including thenear field communication (NFC) signals detected by the kiosk device 108.As such, the token 140 transferred to the kiosk device 108 may cause thekiosk device 108 to issue the ticket items 109 for the requesting user102 and the retrieving user 106. Further, the token 140 may be anencrypted data packet transferred to the kiosk device 108 with thewireless signals 136 to cause the kiosk device 108 to issue the ticketitems 109 for the requesting user 102 and the retrieving user 106. Yet,in some instances, the token 140 may displayed by the retriever device126 in the form of quick response (QR) code that is scanned by the kioskdevice 108 to issue the ticket items 109 for the user 102 and the user106.

In some embodiments, referring to the retriever device 126, theretriever device 126 and/or the system 100 may generate a combinedrequest 142 including the request 112 from the requester device 122,among other possible requests from devices contemplated herein. Further,the combined request 142 may also include a retriever request for one ormore second ticket items from the ticket items 109 provided from thekiosk device 108, such that the requesting user 102 and the retrievinguser 106 may have a respective ticket item from the ticket items 109provided by the kiosk device 108. Further, the retriever device 126 maytransmit the combined request 142 to the kiosk device 108 based on anear field communication (NFC) 136 with the kiosk device 108, among theother forms of communication exchanges with the kiosk device 108described above.

FIG. 1D illustrates the exemplary system 100 with confirmations 158 and160 displayed by the mobile devices 122 and 126, respectively, accordingto an embodiment. As shown, the requester device 122 may include adisplay 152 that provides the confirmation 158 that indicates the item162 is purchased for the user 102, possibly where the item 162corresponds to at least one item from the one or more items 109described above. Further, the display 152 provides the fee 168 istransferred to the user 106, possibly in exchange for the user 106retrieving the item 162 for the user 102. Yet further, the display 152provides the image 170 of the user 106 such that the user 102 may beable to identify the user 106 with the item 162 retrieved from the kioskdevice 108 for the user 102.

Further, as shown, the retriever device 126 may include a display 156that provides the confirmation 160 that corresponds to the confirmation158, as described above. In particular, the confirmation 160 mayindicate the item 162 is purchased for the user 102, possibly where theitem 162 corresponds to at least one item from the one or more items 109described above. Further, the confirmation 160 may indicate the item 164purchased for the user 106, possibly where the item 164 is at least oneitem from the one or more items 109 described above. Yet further, thedisplay 156 provides the fee 168 received from the user 102 and/or theuser 102's account, possibly in exchange for the user 106 retrieving theitem 162 for the user 102. Yet further, the display 156 provides theimage 172 of the user 102 such that the user 106 may be able to identifythe user 102 to pass along the item 162 retrieved from the kiosk device108 for the user 102. Notably, in some instance, the item 162 may haveto be passed to the user 102 for the user 106 to retrieve the fee 168.In particular, based on the user 102 receiving the item 162, the user102 may make an indication on the requester device 122 that the item 162has been received such that the fee 168 may be transferred from the user102's account to the user 106's account, possibly where the accounts aremaintained by a payment provider.

In some embodiments, the system 100 and/or the requester device 122 maydetermine and/or identify the user 102's image 172 to authorize the user106 to retrieve the item 162 from the kiosk device 108 for the retrievalfee 168 described above. In some instances, the retrieval fee 168 may beavailable from the user 102's account, possibly where the requesterdevice 122 is logged into the user 102's account. In some instances, therequest 122 transmitted to the retriever device 126 includes the user102's image 172 to authorize the user 104 to retrieve the item 162 fromthe kiosk device 108 for the retrieval fee 168 from the user 102'saccount. As such, the requester device 122 may display a confirmation158 associated with the retrieval of the item 162 from the kiosk device108 for the retrieval fee 168. As noted, the confirmation 158 mayinclude the retriever image 170, possibly where the retriever image 170is associated and/or linked with the user 106's account.

In some embodiments, the system 100 and/or the requester device 122 maydetermine the global positioning system (GPS) coordinates of therequester device 122 associated with the determined request 112. Assuch, the system 100 and/or the requester device 122 may locate theretriever device 126 from one or more other devices between the GPScoordinates of the requester device 122 and the kiosk device 108. Insome instances, the request 112 may be transmitted to the retrieverdevice 126 based on locating the retriever device 126 from the one ormore other devices between the GPS coordinates of the requester device122 and the kiosk device 108.

In some embodiments, consider the scenarios above where the user 102 maybe in a hurry to get the ticket item 162 from the kiosk device 108,possibly to catch the approaching train. In particular, consider theuser 102 creating the request 112 with the requester device 122. In someinstances, the system 100 and/or the requester device 122 may determinea time period indicated in the determined request 122 to retrieve theitem 162 from the kiosk device 108. For example, the time period mayindicate a short time period, such as three minutes, possibly where thetrain is approaching in three minutes. In some instances, the acceptancemessage 116 from the retriever device 126 may indicate the acceptance toretrieve the item 162 from the kiosk device 108 in the determined and/orspecified time period.

In some embodiments, the system 100 and/or the requester device 122 maydetermine retrieval instructions in the request 112 to retrieve the item162 from the kiosk device 108 for the retrieval fee 168. In someinstances, the request 112 transmitted to the retriever device 126 mayinclude detailed retrieval instructions to retrieve the item 162 fromthe kiosk device 108 for the retrieval fee 168. For example, theretrieval instructions may include instructions for physicallytransferring the item 162 to the user 102, possibly indicating alocation proximate to the kiosk device 108 to transfer the item 162 tothe user 102. Further, in some instances, the acceptance message 116from the retriever device 126 may indicate an acceptance of theretrieval instructions to retrieve the item 162 from the kiosk device108 for the retrieval fee 168, and also possibly transferring and/orpassing the item 162 to the user in accordance with the retrievalinstructions.

In some embodiments, the system 100 and/or the requester device 122 maydetermine an item type associated with the requested item 162. Forexample, the item type may indicate a type of the ticket item 162, suchas a one-way and/or a round-trip ticket item 162, and/or possibly adestination associated with the item 162. Further, the item type mayindicate the type of fare associated with the ticket item 162, anexpress type of the ticket item 162, a particular number assigned to thetrain associated with the ticket item 162, and/or an expirationassociated with the ticket item 162, among other possibilities. In someembodiments, the system 100 and/or the requester device 122 may generatethe token 140 for the retriever device 126 in the form of anauthorization token 140 for the retriever device 126 based on thedetermined item type. As such, the authorization token 140 may providean authorization to retrieve the item 162 from the kiosk device 108 fora retrieval fee 168 from the user 102's account, possibly accessed bythe requester device 122. Notably, the authorization token 140 mayinclude encoded data that indicates the authorization from the user 102such that the user 106 may retrieve the item 162 from the kiosk 108 inexchange for the fee 168. In some instances, the authorization token 140may provide a signature authorization from the user 102 recognized bythe kiosk device 108 such that the user 106 may retrieve the item 162for the user 102 for the fee 168.

In some embodiments, referring back to the retriever device 126, thedevice 126 may receive the request 112 for the one or more items 162from one or more requester devices, such as the requester device 122described above. In some instances, the retriever device 126 may receivethe request 112 based at least on a distance from the retriever device106 to the kiosk device 108, where the distance may be a segment of thedistance 110 described above. The retriever device 126 may alsodetermine an acceptance to retrieve the one or more items 162 from thekiosk device 108 for one or more retrieval fees 168 based on a userinput from the user 106 received by the retriever device 126. Forexample, the acceptance may be determined based on user 106's touchinput received by the retriever device 126. As such, the retrieverdevice 126 may generate and/or transmit the acceptance message 116 tothe one or more requester devices, such as the requester device 122described above. In particular, the acceptance message 116 may begenerated and/or transmitted based on the user 106's input received bythe retriever device 126 that indicates the acceptance that the user 106is retrieving the one or more items 162 from the kiosk device 108 forthe one or more retrieval fees 168.

As shown in FIG. 1D, the retriever device 126 may display theconfirmation 160 based on the user 106 retrieving the one or more items162 from the kiosk device 108 for the user 102. In some instances, theuser 106 may indicate the retrieval of the one or more items 162 throughthe retrieval device 126. Yet, in some instances, the kiosk device 106may detect the retrieval of the one or more items 162 from the kioskdevice 106, such that the kiosk device 106 communicates with therequester device 122 and/or the retriever device 126 and transmits theconfirmations 158 and/or 160, respectively, to the requester device 122and/or the retriever device 126. As noted, for example, the confirmation160 may include one or more requester images 172 that corresponds to theone or more requester devices, such as the requester device 122 of theuser 102. Notably, the confirmation 160 may include other images thatcorrespond to additional requests received from other requesting users.As such, the user 106 may identify the user 102 and possibly other usersthat requested the items 162 and 109. Notably, the retriever device 126may include a non-transitory machine-readable medium includinginstructions. Further, the instructions may be executable to cause theretriever device 126 to perform the various operations described herein.

FIG. 2A illustrates the exemplary system 200 with mobile devices 222,224, and/or 226, according to an embodiment. The users 202, 204, and 206may correspond to the users 102, 104, and 106, respectively. Further,the mobile devices 222 and 226 may correspond to the mobile device 122and 126, respectively. Yet further, the user 104 may have the mobiledevice 224, possibly where the mobile device 224 takes the form of asmartphone, possibly similar to the form of the devices 222 and/or 226described above, perhaps taking the form of wearable computers, laptopcomputers, and/or tablet computers, among other types of computingdevices configured to communicate electronically. The kiosk device 208may correspond to the kiosk device 108 and further, may take the form ofan airline and/or a train ticket kiosk, a ticket counter, a check-outstation, a check-out counter, a point-of-sale (POS) device, an automatedteller machine (ATM) among other possible devices described above.

In some embodiments, the system 200 and/or the devices 222, 224, and/or226 may detect a number of distances 210, 212, and/or 214. For example,the distance 210 may be detected between the mobile device 222 and themobile device 224. Further, the distance 212 may be detected between themobile device 224 and the mobile device 226. Yet further, the distance214 may be detected between the mobile device 226 and the kiosk device208. For example, the requester device 222 may detect the distances 210,212, and/or 214 based on the wireless signals 232, possibly to transmita request 242 to the devices 224 and/or 226. Further, the mobile device224 may detect the distances 210, 212, and/or 214 based on the wirelesssignals 234, possibly to receive the request 242 from the requesterdevice 222 and/or transmit the request 244 to the retriever device 226.Yet further, the retriever device 226 may detect the distance 214 basedon the wireless signals 236, possibly to receive the request 244 and/ortransmit a combined request 246 to the kiosk device 208, possibly wherethe combined request 246 includes, aggregates, and/or represents therequests 242 and/or 244. Further, the kiosk device 208 may receive thecombined request 246 based on the wireless signals 238 of the kioskdevice 208.

Notably, the wireless signals 232, 234, and/or 236 may include theshort-wavelength radio waves in the radio band of 2.4 to 2.485 GHz, suchas Bluetooth®, for example. In some embodiments, the system 200 maydetermine the distances 210-214 based on a triangulation of therespective global positions system (GPS) coordinates of the devices 222,224, and/or 226, among other possibilities to transmit the requests 242,244, and/or 246 over one or more cloud networks.

In some embodiments, the system 200 may generate and/or display therequests 242, 244, and/or 246 on the devices 222, 224, and/or 226 forthe users 202, 204, and/or 206, respectively, possibly based on thedistances 210, 212, and/or 214 detected. For example, the request 242displayed by the requester device 222 may indicate the users 204 and/or206 are within the distances 212 and/or 214 from the kiosk device 108.Further, the request 242 may be generated based on the system 200determining the users 204 and/or 206 may be willing to retrieve an extraticket item 209 for the user 202, possibly based on account information,profile information, and/or transaction histories associated with theusers 204 and/or 206, possibly indicating previous acceptances ofrequests similar to the request 242. As such, the generated request 242may be displayed by the mobile device 222, possibly so the user 202 mayview, modify, and/or change the request 242. Yet, the request 242 mayalso be created by the user 202 with the mobile device 222.

In some embodiments, the system 200 and/or the device 224 may generatethe request 244 based on the request 242 received, possiblyincorporating the request 242 for a first ticket into the request 244for a second ticket, where the first ticket is for user 202 and thesecond ticket is for the user 204. Further, the system 200 and/or thedevice 226 may generate the request 246 based on the request 244received, possibly incorporating the request 242 for the first ticketand the request 244 for the second ticket into the request 244 for athird ticket for the user 206. Thus, the combined request 246 may forthe first ticket, the second ticket, and the third ticket. Notably, thegenerated requests 242, 244, and/or 246 may be transmitted from thedevices 222, 224, and/or 226, respectively, possibly based on respectiveinputs received by the devices 222, 224, and/or 226, such as touchinputs received from the respective users 202, 204, and/or 206, asdescribed above.

FIG. 2B illustrates the exemplary system 200 with the one or more tokens252, 254, and 256, according to an embodiment. As shown, the system 200may include the users 202, 204, and/or 206 described above, along withthe kiosk device 208. Further, the user 202 may have the requesterdevice 222, the user 204 may have the mobile device 224, and the user206 may have the retriever device 226, as described above.

In some embodiments, the system 200 may generate the tokens 252, 254,and/or 256. Further, in some instances, the devices 222, 224, and/or 226may generate the tokens 252, 254, and/or 256, respectively. For example,the system 200 and/or the requester device 222 may generate the token252, possibly encoded in the request 242. Further, the system 200 and/orthe requester device 224 may generate the token 254, possibly encoded inthe request 244. Yet further, the system 200 and/or the requester device226 may generate the token 256, possibly encoded in the request 246.Notably, the tokens 252, 254, and/or 256 may be generated based on thenumber of tickets requested, the type of tickets requested, and/or thecost of the tickets requested, among other requested instructions in therequests 242, 244, and/or 246, as contemplated above. Further, thegenerated tokens 252, 254, and/or 256 may be transmitted to issue and/orretrieve the one or more items 209 from the kiosk device 208 for theusers 202, 204, and/or 206. In particular, the generated tokens 252,254, and/or 256 may be transmitted to the devices 224, 226, and/or 208,respectively, based on the wireless signals 232, 234, and/or 236,possibly including the 2.4 to 2.485 GHz radio waves described above.

In some embodiments, the device 222 may positioned approximately fourcentimeters from the device 224 to transfer the token 252 to the device224, the device 224 may positioned approximately four centimeters fromthe device 226 to transfer the token 254 to the device 226, and thedevice 226 may positioned approximately four centimeters from the kioskdevice 208 to transfer the token 256 to the kiosk device 208. Further,the token 256 may be transferred to the kiosk device 208 based on thewireless signals 236 and/or the near field communication (NFC) signals238 of the kiosk device 208. As such, the token 256 transferred to thekiosk device 208 may cause the kiosk device 208 to issue ticket items209 for the user 202, the user 204, and the user 206, among otherpossible users. As noted above, the token 256 may also be displayed bythe device 226 in the form of a QR code, such that the kiosk device 208may scan the QR code to issue the ticket items 209 for the user 202, theuser 204, and the user 206, among other possible users.

In some embodiments, the system 200 and/or the requester device 224 maydetermine a first token 252 from the request 242 for a first item fromthe one or more items 209, possibly where the first token 252 is encodedin the request 242. Further, the system 200 and/or the requester device224 may generate a second token 254 for the request 244, possibly alsoreferred to as an acceptance message 244 in some instances. Thus, thesecond token 254 may be generated based on the determined first token252, possibly where the second token 254 is generated with the firsttoken 252 encoded in the second token 254. Yet further, the second token254 may be configured to initiate a transaction for the first item and asecond item of the items 209, where the first item may be a first ticketitem for the first user 202 and the second item may be a second ticketitem for the user 204. As such, the acceptance message 244 may includethe second token 254 and may be transmitted to the kiosk device 208 toauthorize the transaction for the first item and the second item,possibly after the user 206 has stepped away from the kiosk device 208in this scenario.

FIG. 2C illustrates the exemplary system 200 with the one or moreconfirmations 258, 260, and/or 262, according to an embodiment. Asshown, the system 200 may include the users 202, 204, and/or 206described above, the corresponding distances 210, 212, and/or 214, andthe kiosk device 208. Further, the user 202 may have the requesterdevice 222, the user 204 may have the requester device 224, and the user206 may have the retriever device 226, as described above.

In some embodiments, one or more of the confirmations 258, 260, and/or262 may be transmitted. In some instances, the confirmation 258 may takethe form of the confirmation 158, possibly including an indication suchas the item 162 purchased for the user 202, the fee 168 transferred tothe user 206, and the image 170 of the user 206. Further, theconfirmation 262 may take the form of the confirmation 160, possiblyincluding an indication such as the item 162 purchased for the user 202,the item 164 purchased for the user 206, the fee 168 transferred fromthe user 202 to the user 206, and the image 172 of the user 202. Yetfurther, the confirmation 262 may indicate at least one item purchasedfor the user 204, a corresponding fee transferred from the user 204'saccount to the user 206's account, and also an image of the user 204.

In some embodiments, the mobile device 224 may perform requester deviceoperations and/or retriever device operations, thereby possibly beingreferred to as the requester device 224 and/or the retriever device 224.As noted, for example, the device 224 may receive the request 242transmitted from the requester device 222, possibly based on thewireless signals 232 described above. Yet, in some instances, theretriever device 224 may receive the request 242 transmitted from theone or more cloud networks of the system 200 described above. As such,the retriever device 224 may display the transmitted request 242. Thus,in response to the transmitted request 242, the retriever device 224 maytransmit the confirmation 258, possibly including the acceptance message116 described above, indicating the user 204 is willing to retrieve anextra item for the user 202 from the one or more items 209 from thekiosk device 208. In particular, the confirmation 258 may be transmittedin response to an input received by the device 224, possibly a touchinput from the user 204.

In some embodiments, referring to retriever device 226, the retrieverdevice 226 and/or the system 200 may receive the confirmation 262 fromthe kiosk device 208 based on the kiosk device 208 issuing the one ormore items 209 and/or the user 206 retrieving the one or more items 209from the kiosk device 208. Further, the retriever device 226 and/or thesystem 200 may transmit the confirmation 260 to the proximate requesterdevice 224 of the one or more requester devices 222 and/or 224, possiblybased on the requester device 224 being closer to the retriever device226. Further, the transmittal of the confirmation 260 to the proximaterequester device 224 may cause a subsequent transmittal of theconfirmation 258 from the proximate requester device 224 to a secondproximate requester device 222, possibly where the subsequenttransmittals are described as trigger transmittals and/or dominotransmittals.

In some embodiments, referring back to FIG. 2B, the system 200 and/orthe device 224 may generate a combined request 244 including the request242 from the requester device 222. The combined request 244 may be for afirst item for the user 202 and a second item for the user 204 from theone or more items 209. The combined request 244 may be transmitted tothe retriever device 226. Further, the user 206 may accept the combinedrequest 244, possibly where an acceptance message, taking the form ofthe acceptance message 116 described above, is transmitted based on thecommunication signals 236 to the requester devices 222 and/or 224. Yet,in some instances, the acceptance message 116 may be transmitted to theone or more cloud networks described above such that the message 116 maybe transferred to the requester devices 222 and/or 224 from the cloudnetworks. It should be noted, in some instances, the combined request244 may include respective proposals from the users 202 and 204 to payrespective retrieval fees in exchange for the user 206 retrieving thefirst item and the second item of the items 209 for the users 202 and204. As such, in some instances, the acceptance message 116 may indicatethe user 206 is willing to retrieve the first and second items of theitems 209 from the kiosk device 208 in exchange for the retrieval fees.

In some embodiments, referring to the retriever device 226, the request244 received from the mobile device 224 may indicate the first request242 for a first item of the items 209 and the second request 244 for asecond item of the items 209. As such, the system 200 and/or theretriever device 226 may determine a first acceptance 258 and a secondacceptance 260 to retrieve the first item and the second item of theitems 209 from the kiosk device 208. For example, the first item may beretrieved by the user 206 for a first retrieval fee from the first user202 and the second item may be retrieved by the user 206 for a secondretrieval fee from the second user 204. For example, the retrieverdevice 226 may determine the first and second acceptances 258 and/or260, respectively, based on the user 206's input to the retriever device226. Notably, the acceptance message, possibly taking the form of theacceptance message 116 described above, may be transmitted to the secondrequester device 224 based on the second acceptance 260 to retrieve thesecond item of the items 209 from the kiosk device 208 for the secondretrieval fee. In some instances, the confirmation displayed by theretriever device 226, possibly taking the form of the confirmation 160,may indicate the retrieval of the second item from the kiosk device 208.As described in the scenarios above, the confirmation 160 displayed mayinclude the one or more requester images, such as the image 172,possibly displaying a second requester image of the user 204 associatedwith the second requester device 224.

FIG. 3 illustrates an exemplary system 300 with the mobile device 222,according to an embodiment. The system 300 may include aspects of thesystems 100 and/or 200 described above in relation to FIGS. 1A-2C. Themobile device 222 shown in FIG. 3 may be the mobile device 222 describedabove in relation to the FIGS. 2A-2C. As shown, the mobile device 222includes a speaker 302, buttons 304, a button 306 with a fingerprintsensor configured to detect a fingerprint from the user 202, a scrollbutton 308 that may move vertically along the input/output (I/O)interface 352, among other components and/or features.

Further, as shown, the mobile device 222 may include the I/O interface352, possibly referred to as a display 352, that renders and/or displaysthe notification 310. The notification 310 may indicate and/or identifythe users ahead of the mobile device 222 in the one or more linesdescribed above, possibly including waiting areas and/or waiting rooms,among various other possibilities. In this example, the notification 310provides, “The following users are ahead of you. Would you like to askthem to buy you items?” Further, the I/O interface 352 displays a list312 of various users including the user 204 provided with the button314, the user 206 provided with the button 316, among other userscontemplated with the ellipses 318, possibly based on longer lines asdescribed above. As such, considering the scenarios above, the user 202may make a selection 320 of the button 314 to select the user 204. Assuch, the request 242 may be transmitted to the mobile device 224, asdescribed above. Notably, the list 312 is shown for purposes ofillustration such that the user 206 with the button 316 may be displayedabove the user 204 with the button 314.

FIG. 4 illustrates an exemplary system 400 with the mobile device 226,according to an embodiment. The system 400 may include aspects of thesystems 100, 200, and/or 300 described above in relation to FIGS. 1A-3.The mobile device 226 shown in FIG. 4 may be the mobile device 226described above in relation to the FIGS. 2A-3. As shown, the mobiledevice 226 includes a speaker 402, buttons 404, a button 406 with afingerprint sensor configured to detect a fingerprint from the user 206,a scroll button 408 that may move vertically along input/output (I/O)interface 456, among other components and/or features.

Further, as shown, the mobile device 226 may include the I/O interface456, possibly referred to as a display 456, that renders and/or displaysthe notification 410. The notification 410 may indicate and/or identifythe users behind the mobile device 226 in the one or more linesdescribed above, possibly including waiting areas and/or waiting rooms,among various other possibilities. In this example, the notification 410provides, “The following users would like you to buy items for them inexchange for fees. Would you like to proceed?” Further, the I/Ointerface 456 displays a list 412 of various users including the user202 provided with the button 414, the user 204 provided with the button416, among other users contemplated with the ellipses 418, possiblybased on longer lines as described above. As such, considering thescenarios above, the user 204 may make a selection 420 of the button 414to select the user 202, possibly accepting the request the 242 describedabove. As such, the acceptance and/or confirmation 258 may betransmitted to the mobile device 222, as described above.

FIG. 5 illustrates an exemplary system with multiple mobile devices 222,224, and/or 226, according to an embodiment. The system 500 may includeaspects of the systems 100, 200, 300, and/or 400 described above inrelation to FIGS. 1A-4. The mobile devices 222, 224, and/or 226 shown inFIG. 5 may be the mobile devices 222, 224, and/or 226 described above inrelation to the FIGS. 2A-4. As shown, the mobile device 222 may includethe input/output (I/O) interface 552 that may take the form of the I/Ointerface 352. The mobile device 224 may include the I/O interface 554may also take similar form the I/O interfaces 352 and/or 456 describedabove. The mobile device 226 may include I/O interface 556 that may takethe form of the I/O interface 456.

As shown, the requester device 222 may display the confirmation 258 onthe I/O interface 552. The confirmation 258 may provide “Item 264Purchased for User 202” and “Fee 270 Transferred to User 206,” possiblyindicating the fee 270 being transferred to the user 206's account forretrieving the item 264 from the kiosk device 208 for the user 202. Theconfirmation 260 may provide “Item 266 Purchased for User 204” and “Fee272 Transferred to User 206,” possibly indicating the fee 272 beingtransferred to the user 206's account for retrieving the item 266 fromthe kiosk device 208 for the user 204. The confirmation 262 may provide“Item 264 Purchased for User 202,” “Item 266 Purchased for User 204,”“Item 268 Purchased for User 206,” “Fee 270 Received from User 202,”“Fee 272 Received from User 204,” possibly indicating the fees 270 and272 being transferred to the user 206's account for retrieving the items264 and 266 from the kiosk device 208 for the users 202 and 204,respectively.

FIG. 6 illustrates an exemplary system 600 with multiple mobile devices222, 224, and 226, according to an embodiment. The system 600 mayinclude aspects of the systems 100, 200, 300, 400, and/or 500 describedabove in relation to FIGS. 1A-5. As shown, the mobile devices 222, 224,and/or 226 in FIG. 6 may be the mobile devices 222, 224, and/or 226,respectively, described above in relation to the FIGS. 2A-5.

As shown on the map 602 with the buildings 604, 606, 608, and/or 610,the mobile device 222 may be at a location 612, the mobile device 224may be at a location 614, and the mobile device 226 may be at a location616 proximate to the kiosk device 208 in the building 610. In someinstances, the mobile device 222 may determine a distance 618 from thelocation 612 of the mobile device 222 to the kiosk device 208 and/or thelocation 616 of the mobile device 226. Further, the mobile device 222may determine a distance 620 from the mobile device 224 to the kioskdevice 208 and/or the location 616 of the mobile device 226. As such,the mobile device 222 may generate the request 242 for the item 264 forthe user 202 based on the distances 618 and/or 620. In some instances,the mobile device 222 may transmit the request 242 to the mobile device224 based on the distance 618 of the mobile device 222 to the kioskdevice 208 being greater than the distance 620 from the mobile device224 to the kiosk device 208. Yet, the mobile device 222 may transmit therequest 242 to the mobile device 226 based on the location 616 of themobile device 226 being proximate to the kiosk device 208, among otherpossibilities.

In some embodiments, the mobile device 224 may determine the distance618 from the location 612 of the mobile device 222 to the kiosk device208 and/or the location 616 of the mobile device 226. Further, themobile device 224 may determine the distance 620 from the mobile device224 to the kiosk device 208 and/or the location 616 of the mobile device226. As such, the mobile device 224 may generate the request 244 for theitem 266 for the user 204 based on the distances 618 and/or 620. Forexample, the mobile device 224 may transmit the request 244 to themobile device 226 based on the distance 618 of the mobile device 222 tothe kiosk device 208 being greater than the distance 214 described abovein FIGS. 2A-2C from the mobile device 226 to the kiosk device 208.

FIG. 7 illustrates an exemplary method 700, according to an embodiment.Notably, one or more steps of the method 700, and/or othermethods/processes described herein may be omitted, performed in adifferent sequence, and/or combined with other methods for various typesof applications contemplated herein.

At step 702, the method 700 may include determining a request from arequester device to retrieve an item. For example, referring back toFIG. 6, the system 600 may determine the request 242 from the requesterdevice 222 to retrieve the item 264 for the user 202, possibly from thekiosk device 208.

At step 704, the method 700 may include transmitting the request to anumber of retriever devices within a distance from the requester deviceto retrieve the item. For example, referring back to FIG. 6, the system600 may transmit the request 242 to a number of retriever devices 224and/or 226 within one or more distances from the requester device 222 toretrieve the item 264. As shown in FIG. 6, the system 600 may transmitthe request 242 to the retriever device 224 that is a distance 622 fromthe requester device 222. Yet, in some instances, the system 600 maytransmit the request 242 to the retriever device 226 that is a distance618 from the requester device 222. Further, the system 600 may transmitthe request 242 to the retriever device 224 based on the distance 620from the retriever device 224 to the kiosk device 208 and/or theretriever device 226. Yet, in some instances, the system 600 maytransmit the request 242 to the retriever device 226 based on thedistance 214 from the retriever device 226 to the kiosk device 208.

At step 706, the method 700 may include, in response to transmitting therequest to the one or more retriever devices, receiving an acceptancemessage from at least one retriever device of the one or more retrieverdevices. For example, in response to transmitting the request 242 to theone or more retriever devices 224 and/or 226, the method 700 may includereceiving an acceptance message, such as the messages 258 and/or 260described above in relation to FIG. 2C, possibly from at least oneretriever device of the one or more retriever devices 224 and/or 226.Notably, the system 600 based on one acceptance message 258, the otheracceptance message 260 may be declined to prevent duplicate acceptancesof the request 242.

At step 708, the method 700 may include, in response to the receivingthe acceptance message, generating a token for at least one retrieverdevice based at least on the determined request for the item. Forexample, in response to the receiving the acceptance message, such asthe messages 258 and/or 260, the method 700 may include generating atoken 252 for at least one of the retriever devices 224 and/or 226 basedon the determined request 242 for the item 264.

At step 710, the method 700 may include transmitting the generated tokento at least on retriever device to retrieve the item. For example, themethod 700 may include transmitting the generated token 252 to one ofthe retriever devices 224 and/or 226 to retrieve the item 264. In suchinstances, the retriever device 224 or retriever device 226 may use thetoken 252, possibly in the form of a quick response (QR) code displayedby the respective devices and scanned by the kiosk device 208. Thus, theretriever device 224 or retriever device 226 that uses the token 252 toretrieve the item 264 first may receive the fee 270. Further, theretriever device 224 or 226 that tries to use the token 252 to after theitem 264 has been retrieved may display a notification that indicatesthe failed attempt to retrieve the item 264 based on the item 264already being retrieved with the token 252.

In some embodiments, the method 700 may include the determining thefirst distance 618 from the requester device 222 to a first retrieverdevice 226 of a number of retriever devices 224, 226, and/or otherpossible retriever devices. Further, the method 700 may includedetermining a second distance 622 from the requester device 222 to thesecond retriever device 224 of number of retriever devices 224, 226,and/or other possible retriever devices. As such, the generated token252 may be transmitted to the first retriever device 226 to retrieve theitem 264 based on the first distance 618 and/or the second distance 622,possibly where the first distance 618 is shorter than the seconddistance 622.

In some embodiments, as noted, the method 700 may include determining afirst retriever device 224 and a second retriever device 226. The method700 may also include determining the first distance 622 from therequester device 222 to the first retriever device 224, a seconddistance 618 from the requester device 222 to the second retrieverdevice 226, and a third distance 214 shown in FIG. 2C from the secondretriever device 226 to the kiosk device 208. As such, the request 242may be transmitted to the second retriever device 226 of the number ofretriever device based on one or more distances from the first distance622, the second distance 618, and the third distance 214. For example,the distance 214 may be shorter than any of the other distances 618,620, and/or 622, such that the request 242 may be transmitted to thesecond retriever device 226 to retrieve the item 264 in the least amountof time.

In some embodiments, the method 700 may include establishing a chaincommunication with the requester device 222. For example, referring toFIG. 2B, there may be a first communication link 232 from the requesterdevice 222 to the first retriever device 224 of the number of retrieverdevices. Further, there may be a second communication link 234 from thefirst retriever device 224 to the second retriever device 226 of thenumber of retriever devices. As such, the method 700 may includetransferring the request 242 from the requester device 222 to the firstretriever device 224 based on the chain communication 232, 234, 236,and/or 238. Further, the method 700 may include generating a secondrequest 244 for a first ticket of the items 209 requested by therequester device 222 and a second ticket of the items 209 requested bythe first retriever device 224 based on the chain communication 232,234, 236, and/or 238. Further, the method 700 may include causing thefirst retriever device 224 to transfer the second request 244 to thesecond retriever device 226 based on the chain communication 232, 234,236, and/or 238.

In some embodiments, referring back to FIG. 2C, the method 700 mayinclude transferring a confirmation 262 to the second retriever device226. The method 700 may also include causing the second retriever device226 to transfer the confirmation 260 to the first retriever device 224based on the chain communication 232, 234, 236, and/or 238. Yet further,the method 700 may include causing the first retriever device 224 totransfer the confirmation 258 to the requester device 22 based on thechain communication 232, 234, 236, and/or 238.

In some embodiments, the method 700 may include causing the secondretriever device 226 to display the confirmation 262 described above inrelation to FIG. 5, possibly associated with the first item 264, thesecond item 266, and the third item 268. The method 700 may also includecausing the first retriever device 224 to display the confirmation 260associated with the second item 266 based on the chain communication232, 234, 236, and/or 238. The method 700 may also include causing therequester device 222 to display the confirmation 258 associated with theitem 264 based on the chain communication 232, 234, 236, and/or 238.

In some embodiments, the number of retriever devices 224 and/or 226 maybe configured to communicate with one or more cloud networks of thesystem 600. As such, the method 700 may include transmitting the request242 to the number of retriever devices 224 and/or 226 by transmittingthe request 242 to the number of retriever devices 224 and/or 226 withthe one or more cloud networks.

As noted in the scenarios above, there may be a predetermined number ofitems that may be retrieved by a single user, possibly at a given time.As such, the method 700 may include determining a first number of items264 requested by the requester device 222. The method 700 may alsoinclude determining a second number of items 266 requested by a firstretriever device 224 of the number of retriever devices 224, 226, and/orother possible devices. The method 700 may also include determining athird number of items 268 requested by a second retriever device 226 ofthe number of retriever devices 224, 226, and/or other possible devices.As such, the method 700 may include transmitting the generated token 252to the first retriever device 224 to retrieve the first number of items264 and the second number of items 266 from the items 209 based on thefirst number of items 264 and the second number of items 266 amountingto less than a predetermined number of items, such as a limited numberof items that may be issued by the kiosk device 208, for example.

FIG. 8 is a block diagram of an exemplary system 800, according to anembodiment. The system 800 may be configured to transfer data over oneor more networks 808 of the system 800, where the one or more networks808 may take the form of the cloud networks and/or base station networksdescribed above in relation to FIGS. 1-7. In particular, the server 802,the client device 804, and/or the client device 806 may each beconfigured to communicate over the communication network 808. As shown,the system 800 includes multiple computing devices but may also includeother possible computing devices. The server 802 may be configured toreceive requests and determine retriever devices. The system 800 mayoperate with more or less than the computing devices shown in FIG. 8,where each device may be configured to communicate over one or morecommunication networks 808, possibly to transfer data accordingly. Insome instances, the one or more communication networks 808 may include adata network and a cellular network, among other possible networks. Insome instances, the communication network 808 may include web servers,network adapters, switches, routers, network nodes, base stations,microcells, and/or various buffers/queues to exchange data/data packets822 and/or 824.

The server 802 may be configured to perform various operations inrelation to the system 800. In some embodiments, the server 802 may beconfigured to receive a request from a client device, such as the clientdevice 804, possibly also referred to as requester device 804. Theserver 802 may also determine one or more other devices, such as theclient device 806, possibly also referred to the retriever device 806.

The data/data packets 822 and/or 824 may be transferrable viacommunication protocols such as Transmission Control Protocol/InternetProtocol (TCP/IP). In various embodiments, each of the data/data packets822 and 824 may be assembled or disassembled into larger or smallerpackets of varying sizes, such as sizes from 1,000 to 1,500 bytes, forexample, among other possible data sizes. As such, data/data packets 822and/or 824 may be transferrable over the network 808 and to variouslocations in the data infrastructure in the system 800.

In some embodiments, the server 802 may take a variety of forms. Theserver 802 may be an enterprise server, possibly operable with one ormore operating systems to facilitate the scalability of the systemand/or the data infrastructure 800. For example, the server 802 mayoperate with a Unix-based operating system configured to integrate witha growing number of other servers, client devices, and/or networks overvarious other systems. The server 802 may further facilitate theworkloads associated with numerous data transfers and workloads in viewof increasing requesting users and/or retrieving users in the datainfrastructure system 800. In particular, the server 802 may facilitatethe scalability of such increasing requesters and sources to eliminatedata congestion, bottlenecks, and/or transfer delays.

In some embodiments, the server 802 may include multiple components,such as one or more processors 812, non-transitory memories 814,non-transitory data storages 816, and/or communication interfaces 818,among other possible components, any of which may be communicativelylinked via a system bus, network, or other connection mechanism 822. Theprocessor 812 may take the form of a multi-purpose processor, amicroprocessor, a special purpose processor, a digital signal processor(DSP) and/or other types of processing components. For example,processor 812 may include a variable-bit (e.g., 64-bit) processorarchitecture configured for scalability and to execute varyinginstructions sets (e.g., simplified and complex instructions sets) withfewer cycles per instruction than other conventional general-purposeprocessors to improve performance of the server 802.

In some embodiments, the processor 812 may perform requester deviceoperations and/or retriever device operations described above, such asgenerating the requests 242, 244, and/or 246. Further, the processor 812may be configured to parse data packets 822 and receive a request from aclient device, such as the requester device 804. As such, the processor812 may identify other client devices, such as the retriever device 806.Referring back to FIGS. 1A-1C, the processor 812 may determine therequest 112 for the one or more items 109 that is available from thekiosk device 108. Thus, the processor 812 may generate the request 112based on the one or more distances 110 from the requester device 112 tothe kiosk device 108, where the requester device 112 may take the formof the requester device 804. Further, processor 812 may communicate withthe requester device 112 with packets 812 to cause the requester device112 to transmit the request 112 to the retriever device 126, where theretriever device 126 may take the form of the retriever device 804, torequest the user 106 to retrieve the one or more items 109 from thekiosk device 108. In some instances, the request 112 may be transmittedto the retriever device 126 based on the wireless signals 132 describedabove. As noted, the request 112 may be transmitted to the retrieverdevice 126 within the distance 110 from the requester device 122 to thekiosk device 108.

The memory component 814 and/or the data storage 816 may include one ormore volatile, non-volatile, and/or replaceable storage components, suchas magnetic, optical, and/or flash storage that may be integrated inwhole or in part with the processor 812. Further, the memory component814 may include or take the form of a non-transitory computer-readablestorage medium, having stored thereon computer-readable instructionsthat, when executed by the processing component 812, cause the server802 to perform machine learning operations, such as those described inthis disclosure and illustrated by the accompanying figures.

The communication interface or component 818 may take a variety of formsand may be configured to allow the server 802 to communicate with one ormore devices, such as client devices 804 and/or 806, according to anumber of protocols. For example, the communication interface 818 mayinclude a transceiver that enables the server 802 to communicate withthe client devices 804 and/or 806 via the one or more communicationnetworks 808. Further, the communication interface 818 may include awired interface, such as an Ethernet interface, and/or a wirelessinterface, such as a cellular interface configured to one or moreprotocols (e.g., GSM, CDMA, UMTS, EV-DO, WiMAX, or LTE) and/or microcellinterface and/or a Wi-Fi interface. The wireless interface may alsoinclude interfaces operable to transfer data over short distancesutilising short-wavelength radio waves in approximately the 2.4 to 2.485GHz range. In some instances, the communication interface 818 maysend/receive data or data packets to/from client devices 804 and/or 806.

The client devices 804 and 806 may also be configured to perform avariety of operations such as those described in this disclosure andillustrated by the accompanying figures. In particular, client devices804 and 806 may be configured to transfer data/data packets 822 and/or824 with the server 802, that include requests to retrieve itemsdescribed above, location data, GPS coordinate data, beacon data, WI-FIdata, base station data, triangulation data, peer data, social mediadata, sensor data, movement data, temperature data, and/or other typesof data described herein.

In some embodiments, the client devices 804 and 806 may include or takethe form of a smartphone system, a personal computer (PC) (e.g., alaptop device), a wearable computer device, a head-mountable display(HMD) device, tablet computer device, a merchant device, a smart watchdevice, other types of wearable devices, and/or other types of computingdevices configured to transfer data, among other possibilities. Theclient devices 804 and 806 may include various components, including,for example, input/output (I/O) interfaces 830 and 840, communicationinterfaces 832 and 842, processors 834 and 844, and data storages 836and 846, respectively, all of which may be communicatively linked witheach other via a system bus, network, or other connection mechanisms 838and 848, respectively.

The I/O interfaces 830 and 840 may be configured to receive inputs fromand provide outputs to one or more users of the client devices 804 and806. For example, the I/O interface 830 may include a graphical userinterface (GUI) configured to receive an input that indicates a requestfor retrieving items as described above. The GUI may also be configuredto receive an input that indicates an acceptance of such requests. Thus,the I/O interfaces 830 and 840 may include input hardware with tangiblesurfaces such as touchscreens with touch sensitive sensors and/orproximity sensors. The I/O interfaces 830 and 840 may be synched with amicrophone configured to receive voice commands, a computer mouse, akeyboard, and/or other input mechanics from the real world environment.In addition, I/O interfaces 830 and 840 may include output hardware suchas touchscreen displays, a sound speaker, other audio output mechanism,a haptic feedback system, and/or other components.

In some embodiments, communication interfaces 832 and 842 may include ortake a variety of forms. For example, communication interfaces 832 and842 may be configured to allow client devices 804 and 806, respectively,to communicate with one or more devices according to a number ofprotocols. For instance, communication interfaces 832 and 842 may beconfigured to allow client devices 804 and 806, respectively, tocommunicate with the server 802 via the communication network 808. Theprocessors 834 and 844 may include a multi-purpose processor, amicroprocessor, a special purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a programmablesystem-on-chip (SOC), field-programmable gate array (FPGA), and/or othertypes of processing components.

The data storages 836 and 846 may include one or more volatile,non-volatile, removable, and/or non-removable storage components, andmay be integrated in whole or in part with processors 834 and 844,respectively. Further, data storages 836 and 846 may include or take theform of non-transitory computer-readable mediums, having stored thereoninstructions that, when executed by processors 834 and 844, cause theclient devices 804 and 806 to perform operations, respectively, such asrequester device and/or retriever device operations described in thisdisclosure and illustrated by the accompanying figures.

In some embodiments, the communication network 808 may be used totransfer data between the server 802, the client device 804, the clientdevice 806, and/or other computing devices associated with the datainfrastructure system 800. The communication network 808 may be apacket-switched network configured to provide digital networkingcommunications and/or exchange data of various forms, content, type,and/or structure. The communication network 808 may include a datanetwork such as a private network, a local area network, and/or a widearea network. Further, the communication network 808 may include acellular network with one or more base station and/or cellular networksof various sizes.

In some embodiments, the client device 804 may create a request possiblyencoded with data/data packet 822 to establish a connection with theserver 802. As such, the request may initiate a search of an internetprotocol (IP) address of the server 802, that may, for example, take theform of the IP address, “192.168.1.102,” for example. In some instances,an intermediate server, e.g., a domain name server (DNS) and/or a webserver, possibly in the one or more networks 808 may identify the IPaddress of the server 802 to establish the connection between the clientdevice 804 and the server 802. As such, the client device 804 mayrequest the server 802 to determine one or more retriever devices 806 ofusers willing to retrieve items as described above.

It can be appreciated that the server 802 and the client devices 804 and806 illustrated in FIG. 8 may be deployed in other ways. The operationsperformed and/or the services provided by such client devices 804 and806 may be combined or separated for a given embodiment and may beperformed by a greater number or a fewer number of devices. Further, oneor more devices may be operated and/or maintained by the same ordifferent entities. Yet, further each device may be associated with oneor more accounts.

In some embodiments, an account, possibly also referred to a useraccount, may be a compilation of data associated with a given user. Someexamples of accounts may include accounts with service providersdescribed above and/or other types of financial, transactional, and/ore-commerce related accounts. Further, accounts may also include socialnetworking accounts, e-mail accounts, smartphone accounts, musicplaylist accounts, video streaming accounts, among other possibilities.For example, an account for a particular user may include data relatedto the user, data related to the user's interest, and/or datarepresenting the user. Further, the user may provide various types ofdata to the account via a user device, e.g., client devices 804 and/or806.

The user account may be displayed on a client device, possibly throughI/O interfaces 830 and/or 840 described above in relation to FIG. 8.Thus, the user account may be displayed on a smartphone system and/orany of the devices described herein to access the account. For example,the user may manage one or more of their accounts on client devices 804and/or 806. In particular, the client device 804 may be used togenerate, view, and/or send one or more requests to transfer funds fromone account to another account, such as an account accessible by theclient device 806.

In some embodiments, a user may have a single account such as an accountwith a service or payment provider described above representing the userfor multiple other accounts. For example, the single user account mayrepresent the user for other e-mail accounts, social networkingaccounts, smartphone accounts, as well as websites, applications, and/orother services. For example, a user could opt to use their account as amulti-purpose account for performing various operations, includingcommunicating with numerous requesters and sources.

In some embodiments, a user account may be created by one or more users.For example, one account may be a family account where a number offamily members or users may have access to the family account. In someinstances, the account may be a corporate account, where employees,staff, worker personnel, and/or contractors, among other individuals mayhave access to the corporate account. Yet further, it should be notedthat a user, as described herein, may be a robot, a robotic system, acomputing device, a computing system, and/or another form of technologycapable of transferring data and/or funds corresponding to the account.A user may be required to provide a login, a password, a code, anencryption key, authentication data, biometric data, and/or other typesof data to access to the account.

The present disclosure, the accompanying figures, and the claims are notintended to limit the present disclosure to the precise forms orparticular fields of use disclosed. As such, it is contemplated thatvarious alternate embodiments and/or modifications to the presentdisclosure, whether explicitly described or implied herein, are possiblein light of the disclosure. Having thus described embodiments of thepresent disclosure, persons of ordinary skill in the art will recognizethat changes may be made in form and detail without departing from thescope of the present disclosure.

1. (canceled)
 2. A system, comprising: a non-transitory memory; and oneor more hardware processors coupled to the non-transitory memory andconfigured to read instructions to cause the mobile device system toperform operations comprising: receiving a request from a user device ofa first user corresponding to a retrieval of a first item from a firstlocation; in response to receiving the request, providing, via a userinterface of the user device, one or more selectable optionscorresponding to one or more retrieving users for the first item; inresponse to receiving a selection, via the user interface of the userdevice, of a first selectable option of the one or more selectableoptions, the first selectable option corresponding to a first retrievinguser of the one or more retrieving users, transmitting a message to adevice of the first retrieving user requesting a confirmation forretrieval of the first item; and in response to receiving theconfirmation from the device of the first retrieving user, transmittinga token to the device of the first retrieving user, wherein the tokenallows for the retrieval of the first item by the first retrieving userfrom the first location.
 3. The system of claim 2, the operationsfurther comprising transmitting a confirmation message to the userdevice of the first user, wherein the confirmation message includesinformation corresponding to the first retrieving user.
 4. The system ofclaim 3, wherein the information corresponding to the first retrievinguser includes one or more images of the first retrieving user.
 5. Thesystem of claim 2, wherein the providing, via the user interface of theuser device, the one or more selectable options corresponding to one ormore retrieving users for the first item includes displaying feeinformation associated with each of the one or more selectable options.6. The system of claim 2, wherein the token, when received by a kioskdevice location at the first location, cause the kiosk device todispense the first item.
 7. The system of claim 2, wherein the token isan authorization token that includes authorization informationassociated with the user.
 8. The system of claim 2, wherein prior to theproviding, via the user interface of the user device, the one or moreselectable options corresponding to one or more retrieving users for thefirst item the operations further comprises identifying the one or moreretrieving users based determining that the one or more retrieving usersbeing within a threshold distance of the first location.
 9. A methodcomprising: receiving a request from a user device of a first usercorresponding to a retrieval of a first item from a first location; inresponse to receiving the request, providing, via a user interface ofthe user device, one or more selectable options corresponding to one ormore retrieving users for the first item; in response to receiving aselection, via the user interface of the user device, of a firstselectable option of the one or more selectable options, the firstselectable option corresponding to a first retrieving user of the one ormore retrieving users, transmitting a message to a device of the firstretrieving user requesting a confirmation for retrieval of the firstitem; and in response to receiving the confirmation from the device ofthe first retrieving user, transmitting a token to the device of thefirst retrieving user, wherein the token allows for the retrieval of thefirst item by the first retrieving user from the first location.
 10. Themethod of claim 9, further comprising transmitting a confirmationmessage to the user device of the first user, wherein the confirmationmessage includes information corresponding to the first retrieving user.11. The method of claim 10, wherein the information corresponding to thefirst retrieving user includes one or more images of the firstretrieving user.
 12. The method of claim 9, wherein the providing, viathe user interface of the user device, the one or more selectableoptions corresponding to one or more retrieving users for the first itemincludes displaying fee information associated with each of the one ormore selectable options.
 13. The method of claim 9 wherein the token,when received by a kiosk device location at the first location, causethe kiosk device to dispense the first item.
 14. The method of claim 9,wherein the token is an authorization token that includes authorizationinformation associated with the user.
 15. The method of claim 9, whereinprior to the providing, via the user interface of the user device, theone or more selectable options corresponding to one or more retrievingusers for the first item the method further comprises identifying theone or more retrieving users based determining that the one or moreretrieving users being within a threshold distance of the firstlocation.
 16. A non-transitory machine-readable medium having storedthereon machine-readable instructions executable to cause a machine toperform operations comprising: receiving a request from a user device ofa first user corresponding to a retrieval of a first item from a firstlocation; in response to receiving the request, providing, via a userinterface of the user device, one or more selectable optionscorresponding to one or more retrieving users for the first item; inresponse to receiving a selection, via the user interface of the userdevice, of a first selectable option of the one or more selectableoptions, the first selectable option corresponding to a first retrievinguser of the one or more retrieving users, transmitting a message to adevice of the first retrieving user requesting a confirmation forretrieval of the first item; and in response to receiving theconfirmation from the device of the first retrieving user, transmittinga token to the device of the first retrieving user, wherein the tokenallows for the retrieval of the first item by the first retrieving userfrom the first location.
 17. The non-transitory machine-readable mediumof claim 16, the operations further comprising transmitting aconfirmation message to the user device of the first user, wherein theconfirmation message includes information corresponding to the firstretrieving user.
 18. The non-transitory machine-readable medium of claim17, wherein the information corresponding to the first retrieving userincludes one or more images of the first retrieving user.
 19. Thenon-transitory machine-readable medium of claim 16, wherein theproviding, via the user interface of the user device, the one or moreselectable options corresponding to one or more retrieving users for thefirst item includes displaying fee information associated with each ofthe one or more selectable options.
 20. The non-transitorymachine-readable medium of claim 16, wherein the token, when received bya kiosk device location at the first location, cause the kiosk device todispense the first item.
 21. The non-transitory machine-readable mediumof claim 16, wherein prior to the providing, via the user interface ofthe user device, the one or more selectable options corresponding to oneor more retrieving users for the first item the operations furthercomprises identifying the one or more retrieving users based determiningthat the one or more retrieving users being within a threshold distanceof the first location.